Release 10.1A: OpenEdge Development:
Progress Dynamics Managers API Reference

askQuestion

This procedure handles the display of all question message types and supports any button combination. The default button list is “OK,CANCEL”. If OK is passed in, the default label to return is OK. Otherwise, the label is the first button in the list. If available, the default cancel button is CANCEL. Otherwise, the first entry in the list is used. The default title is “Question”.

If running server-side, the messages cannot be displayed and must be written to the message log. Because there is no user interface on the server side, the procedure always returns the default button label and answer.

If running client-side, the messages are displayed in a dialog window. The procedure checks the suppressDisplay property in the Session Manager. If the property is set to YES, the procedure does not display the message. It passes the message to the log. This is useful when running take-on procedures on the client side.

The messages are passed to the procedure, af\app\afmessagep.p, on the AppServer for interpretation. This procedure performs the necessary tasks to return the formatted messages. This might include the following tasks:

Formatting the messages appropriately.
Reading the text from the Progress Dynamics message file.
Interpreting the carrot-delimited lists that come back from triggers.
Dealing with ADM2 CHR(4)-delimited messages.
Translating the message if required.

Once the messages are formatted, a client-side message displays using the standard Progress Dynamics message dialog box. On the server-side, the Progress Dynamics error log is updated with the error and, if possible, an e-mail is sent to the currently logged-in user to notify them. This process also occurs if the error log flag is set to YES or message display suppression is enabled.

Location: af\app\afsesmngrp.i

Parameters:

INPUT pcMessageList AS CHARACTER INPUT pcButtonList AS CHARACTER INPUT pcDefaultButton AS CHARACTER INPUT pcCancelButton AS CHARACTER INPUT pcMessageTitle AS CHARACTER INPUT pcDataType AS CHARACTER INPUT pcFormat AS CHARACTER INPUT-OUTPUT pcAnswer AS CHARACTER OUTPUT pcButtonPressed AS CHARACTER Notes: When running client-side, the procedure returns the untranslated button text of the pressed button. When running server-side, the untranslated button text of the default button is returned.

Examples: See the logMessage procedure in af\cod2\fulloobjcw.w.